Version 1.00

SYSLOG monitors the ISDN usage of cisco routers.
It supports BRI and PRI's
Also is it possible to log conssole messages to files (syslog server)
It is designed for small / medium size networks.

Syslog generates every day 2 files :

    mm-dd-yy.CSV        has one line for every starting ISDN call.
                        and one line for every ISDN call when it terminates.
    mm-dd-yy.LOG        contains alle console messages from all reporting routers
                        and or unix hosts
                        also diagnostic messages of SYSLOG itself are 
			written into this files.

There is a graphic display in the main screen which gives an overview
over the ISDN usage of the last 10 days

Syslog runs over winsock and should run on top of Windows 3.11 / Win95 and NT
It has been tested with cisco IOS 10.3(8) and higher.

Installation of this application:

1. Unzip all files into one directory. e.g. :C:\syslog

2. Create a shortcut to start SYSLOG.EXE (NOT syslog-i.exe !)
   Or start it by hand by starting syslog.exe

3. In de windows directory : edit the file HOSTS. If it not exists create it.
   For NT :  \<winnt>\system32\drivers\etc
   After installation of windows there is a file HOST.SAM (sample file).
   which you can use to investigate.

   For every router that generates ISDN traps (NOT the remote routers !!),
   enter a line which contains the IP address and the name of this router.
   example :

145.215.20.1    rtr-isdn
145.215.21.1    rtr-isdn
145.215.22.1    rtr-isdn

   Note : all interfaces of the same router are entered here. Due to a bug
          in the IOS, the router will not alway's give the same source
          address in the isdn-snmp trap.
          (the config statement "snmp-server trap-source Ethernet 0" does
           not work correctly in some older releases.)

   If a router uses a trap source address that is not in the HOST file there
   will be a line in the log file :

   DNS lookup failed for 145.215.23.1

   If you see this happen please insert this ip address + name also in the
   HOSTS file.


CISCO-ROUTER config:
For every router that generates ISDN traps the following statements must
be configured:

Note : these routers are LOCAL to the PC where syslog runs, in many
       cases this will be only one - central site - router)


 
1.      snmp-server community public ro
        snmp-server trap-source Ethernet 0
        snmp-server enable traps isdn
        snmp-server host nn.nn.nn.nn public isdn   ;nn.nn.nn.nn is ip
                                                   ;address of syslog PC

2. At every PRI, BRI or (isdn) DIALER interface :
        no snmp trap link-status


3. If you also want to log console messages :

        logging nn.nn.nn.nn      ;nn.nn.nn.nn is ip-address of syslog-pc



If you have configured it sofar, test the application and see if it basicly
works. If so add then the information needed for synchronisation into
the file : SYSLOG.RTR
add for every router that generates ISDN traps (again NOT the remote routers):
ip-address-off-router,vty-password
example:
	129.23.34.5,cisco

Again this is the vty password of the router NOT the enable password.
If the IP address + name is in the HOST file you can also specify the
name of the router.
SYSLOG uses this info at startup time to synchronize itself with the
router(s). If the ip address is wrong it will time-out very slowly (4 minutes)



Known problems :


1. This version is driven by SNMP TRAPS.
   For this reason it cannot run on PC where ANTOTHER snmp management system
   runs (e.g. cisco works).

2. Because this program is passive it can happen that it is not longer
   synchronised with the router(s) if SNMP traps are lost.
   For this reason the program is stopped automaticly at 23:59 and restarted
   at 00:00.
   At program startup time it is synchronized with the configured routers.
   (SYSLOG.RTR)

3. Keep in mind that snmp traps are UDP messages (not session oriented, so
   it can happen that traps are lost).


For more detailed info see the online help info.


By using this program you agree that you use it on a "as is" base.
Author does not take any resposibillity for unwanted behaviour.

